Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4851bc31a12c472e2db6701a2e1ce281f1f070d0167758f62c535b5cd16edf31

Tx prefix hash: 077f4d886ed2840b59e2540e8312e017b0da525f0e020566d6ba41aafd95ec3a
Tx public key: 39d10efa4ad4cff7447be18da12a16117c6b9671f32f25efde622ff5e4a4d281
Timestamp: 1734164896 Timestamp [UCT]: 2024-12-14 08:28:16 Age [y:d:h:m:s]: 00:187:03:42:48
Block: 1174898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133434 RingCT/type: yes/0
Extra: 0139d10efa4ad4cff7447be18da12a16117c6b9671f32f25efde622ff5e4a4d2810211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e261165eae5cb0986dfef5d438efff9b07c3ec8393ce8dd1c1e5e8bfdee71ca 0.600000000000 1661107 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": 1174908, "vin": [ { "gen": { "height": 1174898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e261165eae5cb0986dfef5d438efff9b07c3ec8393ce8dd1c1e5e8bfdee71ca" } } ], "extra": [ 1, 57, 209, 14, 250, 74, 212, 207, 247, 68, 123, 225, 141, 161, 42, 22, 17, 124, 107, 150, 113, 243, 47, 37, 239, 222, 98, 47, 245, 228, 164, 210, 129, 2, 17, 0, 0, 0, 4, 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