Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e375856654c4767cd2b3553f5fcbe29b8a9d261dd323ae9818d74cfad373e375

Tx prefix hash: 495a6a74558e12e9fda645644ef6292c45039e3d08dc0f27cff05f70a71321ec
Tx public key: 5de811dd0e243c9fc33d2fdfa3a7ba526489018d5b6f6922e7e6c656c05d5821
Timestamp: 1716008950 Timestamp [UCT]: 2024-05-18 05:09:10 Age [y:d:h:m:s]: 00:196:03:20:22
Block: 1024467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140404 RingCT/type: yes/0
Extra: 015de811dd0e243c9fc33d2fdfa3a7ba526489018d5b6f6922e7e6c656c05d58210211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 925c4afedc64c292e6e8285b3950972fb40adfe8f4edb905429f8371dd381ee8 0.600000000000 1490240 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": 1024477, "vin": [ { "gen": { "height": 1024467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "925c4afedc64c292e6e8285b3950972fb40adfe8f4edb905429f8371dd381ee8" } } ], "extra": [ 1, 93, 232, 17, 221, 14, 36, 60, 159, 195, 61, 47, 223, 163, 167, 186, 82, 100, 137, 1, 141, 91, 111, 105, 34, 231, 230, 198, 86, 192, 93, 88, 33, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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