Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9783e65a757b47d9d6a5a5dc2af66d1a4673dc2268a30673b700cf648d5879

Tx prefix hash: d0773e8e87d05cabb69e66dc6217ae67fbee0a8cdf796884815b7dc652818b9e
Tx public key: 0cd87e77ce41fc67bde64fc71d891a7006e63fd3494a79b0df2f503c8a12d430
Timestamp: 1584839707 Timestamp [UCT]: 2020-03-22 01:15:07 Age [y:d:h:m:s]: 04:255:21:31:05
Block: 86437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1079568 RingCT/type: yes/0
Extra: 010cd87e77ce41fc67bde64fc71d891a7006e63fd3494a79b0df2f503c8a12d4300211000000068a2ee0d9000000000000000000

1 output(s) for total of 317.428916127000 dcy

stealth address amount amount idx
00: c7b1168b0cbb8580d97ed86ea2709eeab50a61eed40f621542b38821ae26f498 317.428916127000 155935 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": 86447, "vin": [ { "gen": { "height": 86437 } } ], "vout": [ { "amount": 317428916127, "target": { "key": "c7b1168b0cbb8580d97ed86ea2709eeab50a61eed40f621542b38821ae26f498" } } ], "extra": [ 1, 12, 216, 126, 119, 206, 65, 252, 103, 189, 230, 79, 199, 29, 137, 26, 112, 6, 230, 63, 211, 73, 74, 121, 176, 223, 47, 80, 60, 138, 18, 212, 48, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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