Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca546966f0d8bb56406f0ee0553061ed38ad3abe0d56c35df4adc2b6216536bc

Tx prefix hash: 07bdcf6966171d95f59ea3332994e346cd50e98aadc9a7c3aeb256f66aa39841
Tx public key: 3ae42e834984e083b8c97419caada4a9fac2ff18f2bf8b8c3c9e00303456b402
Timestamp: 1735389177 Timestamp [UCT]: 2024-12-28 12:32:57 Age [y:d:h:m:s]: 00:169:17:27:30
Block: 1185009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121042 RingCT/type: yes/0
Extra: 013ae42e834984e083b8c97419caada4a9fac2ff18f2bf8b8c3c9e00303456b4020211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 966ab8affe07f2255961527a5a0dbf112a4404b948cbca336a5bc1935a0bcdc3 0.600000000000 1671474 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": 1185019, "vin": [ { "gen": { "height": 1185009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "966ab8affe07f2255961527a5a0dbf112a4404b948cbca336a5bc1935a0bcdc3" } } ], "extra": [ 1, 58, 228, 46, 131, 73, 132, 224, 131, 184, 201, 116, 25, 202, 173, 164, 169, 250, 194, 255, 24, 242, 191, 139, 140, 60, 158, 0, 48, 52, 86, 180, 2, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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