Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74955f2ff2c32f14264c1b8cf61022b7e204afcac5e42b250f862a3f5ccb90bb

Tx prefix hash: d0f8080a8749134911ac074260d255ffb6f3e0c2d5aecd85d7994d75a1afbd2d
Tx public key: 920a2f57e55e572d50d1b914a11db5d30fc096920e3318db12ff287db3628c99
Timestamp: 1715393184 Timestamp [UCT]: 2024-05-11 02:06:24 Age [y:d:h:m:s]: 00:338:19:39:28
Block: 1019381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242170 RingCT/type: yes/0
Extra: 01920a2f57e55e572d50d1b914a11db5d30fc096920e3318db12ff287db3628c9902110000000441ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ccd9bd50bf1c49a12da5ae867e60892eb6def720ceb3c1d5f9b36acc45f79af 0.600000000000 1483334 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": 1019391, "vin": [ { "gen": { "height": 1019381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ccd9bd50bf1c49a12da5ae867e60892eb6def720ceb3c1d5f9b36acc45f79af" } } ], "extra": [ 1, 146, 10, 47, 87, 229, 94, 87, 45, 80, 209, 185, 20, 161, 29, 181, 211, 15, 192, 150, 146, 14, 51, 24, 219, 18, 255, 40, 125, 179, 98, 140, 153, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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