Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3676d660e991eb8e0f5c9e4d0060d235cfb960e8a3461a188b30625dd887c945

Tx prefix hash: b94dcbab32ca36c0f9007d5dc2a513864fc6c664398082ac9423e354badd79ab
Tx public key: 3cad16f551887050860cb348378fe1131f8030ec091e30c9783d7d7a67b4c2a4
Timestamp: 1727061531 Timestamp [UCT]: 2024-09-23 03:18:51 Age [y:d:h:m:s]: 00:110:09:48:13
Block: 1116101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78937 RingCT/type: yes/0
Extra: 013cad16f551887050860cb348378fe1131f8030ec091e30c9783d7d7a67b4c2a402110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb6acb0565f2f2ad84582b0d8b847e6add4cd6820dff6b87af7fa549bcf6cec1 0.600000000000 1596468 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1116111, "vin": [ { "gen": { "height": 1116101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb6acb0565f2f2ad84582b0d8b847e6add4cd6820dff6b87af7fa549bcf6cec1" } } ], "extra": [ 1, 60, 173, 22, 245, 81, 136, 112, 80, 134, 12, 179, 72, 55, 143, 225, 19, 31, 128, 48, 236, 9, 30, 48, 201, 120, 61, 125, 122, 103, 180, 194, 164, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8