Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86d139a30672cf570c6223a969a8d7df7425f6c61f62356ecb3e3278519865c9

Tx prefix hash: a68577c5246abde9d4898fbfdd1dc6bafee8564be36b2c3c8994baf582df1292
Tx public key: a5eb6024bf926f3719d54bd5057edced8a197713ea1bf8e378a1fba2d56a0063
Timestamp: 1634848722 Timestamp [UCT]: 2021-10-21 20:38:42 Age [y:d:h:m:s]: 03:065:06:07:22
Block: 357647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 824938 RingCT/type: yes/0
Extra: 01a5eb6024bf926f3719d54bd5057edced8a197713ea1bf8e378a1fba2d56a00630211000000077e786c8c000000000000000000

1 output(s) for total of 40.083666034000 dcy

stealth address amount amount idx
00: bc72054f3bf6bf0ef2ddb0409d30d54ec2a4bca58b7b90e46963ed530dacef68 40.083666034000 729195 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": 357657, "vin": [ { "gen": { "height": 357647 } } ], "vout": [ { "amount": 40083666034, "target": { "key": "bc72054f3bf6bf0ef2ddb0409d30d54ec2a4bca58b7b90e46963ed530dacef68" } } ], "extra": [ 1, 165, 235, 96, 36, 191, 146, 111, 55, 25, 213, 75, 213, 5, 126, 220, 237, 138, 25, 119, 19, 234, 27, 248, 227, 120, 161, 251, 162, 213, 106, 0, 99, 2, 17, 0, 0, 0, 7, 126, 120, 108, 140, 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