Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6541608fe7c91093e6384f32e1d2ade40002dfd4adac053d695718c814f8284

Tx prefix hash: 82d121f939928e9bee974c29fdfd2bad7014d9ab811ac7cd4607444f89480360
Tx public key: 03e8e03405c0b4590cf1ab07d616604c35d0c77bb9423c24a39b71c257069008
Timestamp: 1712580912 Timestamp [UCT]: 2024-04-08 12:55:12 Age [y:d:h:m:s]: 01:070:13:30:54
Block: 996020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311336 RingCT/type: yes/0
Extra: 0103e8e03405c0b4590cf1ab07d616604c35d0c77bb9423c24a39b71c25706900802110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3458782a544e53f9423e360a58a87f8d1b681d67ba3e5f580bc05cb8ecfd597f 0.600000000000 1456436 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": 996030, "vin": [ { "gen": { "height": 996020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3458782a544e53f9423e360a58a87f8d1b681d67ba3e5f580bc05cb8ecfd597f" } } ], "extra": [ 1, 3, 232, 224, 52, 5, 192, 180, 89, 12, 241, 171, 7, 214, 22, 96, 76, 53, 208, 199, 123, 185, 66, 60, 36, 163, 155, 113, 194, 87, 6, 144, 8, 2, 17, 0, 0, 0, 9, 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