Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd4e2202580734bf3fe3f284ceeebdaf42f9a10ec1ad507ae6f0079fc097cbd0

Tx prefix hash: 893999e51e16ca6eba5f967ab81351743df986cff2753553f7e47be0e075959b
Tx public key: 0a0b0cab7a7d741af3fbd5a6574e12e000fdf3e889d650ca8073e68905611731
Timestamp: 1706782117 Timestamp [UCT]: 2024-02-01 10:08:37 Age [y:d:h:m:s]: 01:096:05:23:21
Block: 947952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329878 RingCT/type: yes/0
Extra: 010a0b0cab7a7d741af3fbd5a6574e12e000fdf3e889d650ca8073e689056117310211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92dcdeadf0a062167b4e6b02b98c9a54f2886de38363c22168aacf3ec2fa96b0 0.600000000000 1406314 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": 947962, "vin": [ { "gen": { "height": 947952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92dcdeadf0a062167b4e6b02b98c9a54f2886de38363c22168aacf3ec2fa96b0" } } ], "extra": [ 1, 10, 11, 12, 171, 122, 125, 116, 26, 243, 251, 213, 166, 87, 78, 18, 224, 0, 253, 243, 232, 137, 214, 80, 202, 128, 115, 230, 137, 5, 97, 23, 49, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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