Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 905b826e54f1cc9f16f22e2e00aec2df7372bfce9fa3169efd87e356507845ef

Tx prefix hash: 3b06250c0f14580b5ece1247a90a44f67dac69345410a0775a6e426a11699356
Tx public key: 6de856088d98721f5b8b59460c0efa794a9ae030cf4730d8f7ebca65873db3d0
Timestamp: 1695218168 Timestamp [UCT]: 2023-09-20 13:56:08 Age [y:d:h:m:s]: 01:234:15:30:20
Block: 852292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428801 RingCT/type: yes/0
Extra: 016de856088d98721f5b8b59460c0efa794a9ae030cf4730d8f7ebca65873db3d002110000000733af99f4000000000000000000

1 output(s) for total of 0.920455621000 dcy

stealth address amount amount idx
00: 03d0b3b03fae206f01c16503a29a6e0a8f68db6f1ccfa9e04c6968d456f19ab5 0.920455621000 1306120 of 0

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": 852302, "vin": [ { "gen": { "height": 852292 } } ], "vout": [ { "amount": 920455621, "target": { "key": "03d0b3b03fae206f01c16503a29a6e0a8f68db6f1ccfa9e04c6968d456f19ab5" } } ], "extra": [ 1, 109, 232, 86, 8, 141, 152, 114, 31, 91, 139, 89, 70, 12, 14, 250, 121, 74, 154, 224, 48, 207, 71, 48, 216, 247, 235, 202, 101, 135, 61, 179, 208, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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