Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da007d0034d7628acf173bd568117456522c30b1a7787a4e0d446980d076f7be

Tx prefix hash: 62ea9a371f66cb99fc48de2b7387f32dab149ac31ee0d4684ffa537b4803d094
Tx public key: fe8b092c7f522527170e4bf51d6a5c9a4d953ac2d75a2674f8c51e23e1e04303
Timestamp: 1710308039 Timestamp [UCT]: 2024-03-13 05:33:59 Age [y:d:h:m:s]: 01:065:15:42:13
Block: 977215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307923 RingCT/type: yes/0
Extra: 01fe8b092c7f522527170e4bf51d6a5c9a4d953ac2d75a2674f8c51e23e1e0430302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 600250056329411784f1802c2b669e2cd2a0d7c2348d04d3cffc3a2949c4599d 0.600000000000 1437216 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": 977225, "vin": [ { "gen": { "height": 977215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "600250056329411784f1802c2b669e2cd2a0d7c2348d04d3cffc3a2949c4599d" } } ], "extra": [ 1, 254, 139, 9, 44, 127, 82, 37, 39, 23, 14, 75, 245, 29, 106, 92, 154, 77, 149, 58, 194, 215, 90, 38, 116, 248, 197, 30, 35, 225, 224, 67, 3, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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