Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20fa2339d996c6932ff1d9a79ecdf4ad8e6ab48e94c0c1efb2fd55835d37fe74

Tx prefix hash: 7f506c45270059f646a112490f3b6e4b7f7b5e3b5bae26f0c613f86cf7b99244
Tx public key: c55b1442b939fbe8dda1fd6a01ab749d1edcf0bc4ad8fa4557b4ababa320a0da
Timestamp: 1724313518 Timestamp [UCT]: 2024-08-22 07:58:38 Age [y:d:h:m:s]: 00:213:01:24:39
Block: 1093336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152118 RingCT/type: yes/0
Extra: 01c55b1442b939fbe8dda1fd6a01ab749d1edcf0bc4ad8fa4557b4ababa320a0da021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 255e75401f7415132b024e5a58e353e5a5bf9f56967fa9299898bec4bead0b5e 0.600000000000 1568259 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": 1093346, "vin": [ { "gen": { "height": 1093336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "255e75401f7415132b024e5a58e353e5a5bf9f56967fa9299898bec4bead0b5e" } } ], "extra": [ 1, 197, 91, 20, 66, 185, 57, 251, 232, 221, 161, 253, 106, 1, 171, 116, 157, 30, 220, 240, 188, 74, 216, 250, 69, 87, 180, 171, 171, 163, 32, 160, 218, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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