Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 056d140a1215eb2904b81629d5a3808e7f089541f95f7a09124ae81a925d1758

Tx prefix hash: dd89d0c532a14d3fd39fd6a9adc07d5dd0bb89ffbebb791aa62f8187876e4e6f
Tx public key: 3659a29659f69f5791a7c2aec721a07f84ad5c5e1f3ef893b5fb16bf7e61d5f3
Timestamp: 1639173213 Timestamp [UCT]: 2021-12-10 21:53:33 Age [y:d:h:m:s]: 02:343:11:47:29
Block: 392764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 763543 RingCT/type: yes/0
Extra: 013659a29659f69f5791a7c2aec721a07f84ad5c5e1f3ef893b5fb16bf7e61d5f3021100000019e9564d6f000000000000000000

1 output(s) for total of 30.662685314000 dcy

stealth address amount amount idx
00: 214ed35fe4e878dde49911407e7b82993d9e1c025c6c61320ce19955765949a0 30.662685314000 789763 of 0

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": 392774, "vin": [ { "gen": { "height": 392764 } } ], "vout": [ { "amount": 30662685314, "target": { "key": "214ed35fe4e878dde49911407e7b82993d9e1c025c6c61320ce19955765949a0" } } ], "extra": [ 1, 54, 89, 162, 150, 89, 246, 159, 87, 145, 167, 194, 174, 199, 33, 160, 127, 132, 173, 92, 94, 31, 62, 248, 147, 181, 251, 22, 191, 126, 97, 213, 243, 2, 17, 0, 0, 0, 25, 233, 86, 77, 111, 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