Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beb08b5a353e38aabc77f3665acff75c5db11b161d1f6f80378f72f724aa4578

Tx prefix hash: 1c2a23b8cdee01afdb77decd294894d4baae4c3bd0485b7edd419d431ac4f5a9
Tx public key: 1c0da80f0ad4dd49b0226c41efb5c9200db857350c66f199f6fe5cafc04d297a
Timestamp: 1708767265 Timestamp [UCT]: 2024-02-24 09:34:25 Age [y:d:h:m:s]: 01:259:11:35:41
Block: 964438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444189 RingCT/type: yes/0
Extra: 011c0da80f0ad4dd49b0226c41efb5c9200db857350c66f199f6fe5cafc04d297a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 816ac40ea11bd8810c661822787bfa42e8cb17e39f63ae284fbfc9488d84cd28 0.600000000000 1424173 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": 964448, "vin": [ { "gen": { "height": 964438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "816ac40ea11bd8810c661822787bfa42e8cb17e39f63ae284fbfc9488d84cd28" } } ], "extra": [ 1, 28, 13, 168, 15, 10, 212, 221, 73, 176, 34, 108, 65, 239, 181, 201, 32, 13, 184, 87, 53, 12, 102, 241, 153, 246, 254, 92, 175, 192, 77, 41, 122, 2, 17, 0, 0, 0, 5, 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