Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fca88de874a03725330eb350d86031a4cd83647369ff6165a216a2a0b52b55f

Tx prefix hash: bd7df096036e3c3ae907d0e13b4594668ba5c79b36c5cf452d5e19181334613c
Tx public key: a7c88acc1b9c76d435f0dc88674fe87d130131cebb2c763bf7ee7d3619b69819
Timestamp: 1715654177 Timestamp [UCT]: 2024-05-14 02:36:17 Age [y:d:h:m:s]: 00:305:20:42:03
Block: 1021524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218649 RingCT/type: yes/0
Extra: 01a7c88acc1b9c76d435f0dc88674fe87d130131cebb2c763bf7ee7d3619b698190211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c5a5b25f31ce734055830cbf9de293065e6e4d8c28ca63afca666f22c3e8b9e 0.600000000000 1485869 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": 1021534, "vin": [ { "gen": { "height": 1021524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c5a5b25f31ce734055830cbf9de293065e6e4d8c28ca63afca666f22c3e8b9e" } } ], "extra": [ 1, 167, 200, 138, 204, 27, 156, 118, 212, 53, 240, 220, 136, 103, 79, 232, 125, 19, 1, 49, 206, 187, 44, 118, 59, 247, 238, 125, 54, 25, 182, 152, 25, 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