Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e4e5b71809e6c66e25eb63d03c6570c111794c89f69976f9546ba3be51139ea

Tx prefix hash: 7e54ea8a4a4089740f8820113f759d05b280220ed9ceb8499cec0e926096ecd3
Tx public key: 0fd79bde9baaff1bcbe05c3ffeb8a91f2c6c350b4e59e2a0594a3d2f224c292f
Timestamp: 1718859272 Timestamp [UCT]: 2024-06-20 04:54:32 Age [y:d:h:m:s]: 00:327:12:12:42
Block: 1048102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234063 RingCT/type: yes/0
Extra: 010fd79bde9baaff1bcbe05c3ffeb8a91f2c6c350b4e59e2a0594a3d2f224c292f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98722975c8bf3ac07976b9f2aa1d4f582c5834e59b94fb342b7e2024a782081f 0.600000000000 1518097 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": 1048112, "vin": [ { "gen": { "height": 1048102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98722975c8bf3ac07976b9f2aa1d4f582c5834e59b94fb342b7e2024a782081f" } } ], "extra": [ 1, 15, 215, 155, 222, 155, 170, 255, 27, 203, 224, 92, 63, 254, 184, 169, 31, 44, 108, 53, 11, 78, 89, 226, 160, 89, 74, 61, 47, 34, 76, 41, 47, 2, 17, 0, 0, 0, 2, 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