Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2485684089c5dc16c6cb402f79f0d1bcd173ae4a71aaaa6159041df9d7884d56

Tx prefix hash: 98bc07d84cb8af3089ecf608e19ede576de888c68b47273132b9edea2116e218
Tx public key: 346ec72d488e850c61b7fdc9a2e0362be1a5150b4c7b77e3a15ce7ca3d7b7220
Timestamp: 1705918719 Timestamp [UCT]: 2024-01-22 10:18:39 Age [y:d:h:m:s]: 00:355:08:31:17
Block: 940780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254432 RingCT/type: yes/0
Extra: 01346ec72d488e850c61b7fdc9a2e0362be1a5150b4c7b77e3a15ce7ca3d7b72200211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9403e9df4d8501910cbf608c67796ca8648e3a02ac59c8a274452a17ad08f65c 0.600000000000 1398920 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": 940790, "vin": [ { "gen": { "height": 940780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9403e9df4d8501910cbf608c67796ca8648e3a02ac59c8a274452a17ad08f65c" } } ], "extra": [ 1, 52, 110, 199, 45, 72, 142, 133, 12, 97, 183, 253, 201, 162, 224, 54, 43, 225, 165, 21, 11, 76, 123, 119, 227, 161, 92, 231, 202, 61, 123, 114, 32, 2, 17, 0, 0, 0, 3, 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