Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22796788cd0b4a505fc0c0610e8be33e18ac384a56bfbe8f9030e49641792a5

Tx prefix hash: 750644c16f1b77fc274bd0343816515d55fe0323dbee13a97dc7c2fdcca6bb24
Tx public key: 2203bf53f6a08b2efc01e2d3a3b555a18cf1bb51b7a17b7be96db22807ad70c7
Timestamp: 1705162519 Timestamp [UCT]: 2024-01-13 16:15:19 Age [y:d:h:m:s]: 01:068:06:48:28
Block: 934534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309893 RingCT/type: yes/0
Extra: 012203bf53f6a08b2efc01e2d3a3b555a18cf1bb51b7a17b7be96db22807ad70c70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5ffe434c5ecd52358a9daacad7f5560b9ffffb878c65e6e9d5a02e77d0edf45 0.600000000000 1392548 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": 934544, "vin": [ { "gen": { "height": 934534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5ffe434c5ecd52358a9daacad7f5560b9ffffb878c65e6e9d5a02e77d0edf45" } } ], "extra": [ 1, 34, 3, 191, 83, 246, 160, 139, 46, 252, 1, 226, 211, 163, 181, 85, 161, 140, 241, 187, 81, 183, 161, 123, 123, 233, 109, 178, 40, 7, 173, 112, 199, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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