Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64001abfc5f72d50a1fbf6b3cabf1df9a4988c4bb041df439a667f75f5de14fe

Tx prefix hash: 3e83cdcf96851dad0e83238158b85d95c34f8051a608112da64d36af2f981a4a
Tx public key: 6d8b53b4046f8b6647d30f7872e4f1cbdbaa676c6e01ee0e6928240f8c17131b
Timestamp: 1730927065 Timestamp [UCT]: 2024-11-06 21:04:25 Age [y:d:h:m:s]: 00:017:05:39:23
Block: 1148056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12346 RingCT/type: yes/0
Extra: 016d8b53b4046f8b6647d30f7872e4f1cbdbaa676c6e01ee0e6928240f8c17131b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bccda2fd2950246f57b6d4431eea5605d31bfe068ad731af636597549558f69 0.600000000000 1632811 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": 1148066, "vin": [ { "gen": { "height": 1148056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bccda2fd2950246f57b6d4431eea5605d31bfe068ad731af636597549558f69" } } ], "extra": [ 1, 109, 139, 83, 180, 4, 111, 139, 102, 71, 211, 15, 120, 114, 228, 241, 203, 219, 170, 103, 108, 110, 1, 238, 14, 105, 40, 36, 15, 140, 23, 19, 27, 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