Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 400adea65d734e83a61dbedab7c0bf9979909f7a48a3ba4f79a6a0eb11f4eb33

Tx prefix hash: 80b5ef3367248ceff4a0efa950e608c8ab83018500c002d96d3acff2ee52966a
Tx public key: 294d9f46f807ad7448d59992ccecc0fb55d4bb13bf2940da0e6ee31e2a2ddc1d
Timestamp: 1714617032 Timestamp [UCT]: 2024-05-02 02:30:32 Age [y:d:h:m:s]: 00:350:21:35:45
Block: 1012932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250828 RingCT/type: yes/0
Extra: 01294d9f46f807ad7448d59992ccecc0fb55d4bb13bf2940da0e6ee31e2a2ddc1d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 053242b3ad7198179ab72a5d4ed6fc2c852840cba0ed4fafda2fc3875b22bb3a 0.600000000000 1475605 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": 1012942, "vin": [ { "gen": { "height": 1012932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "053242b3ad7198179ab72a5d4ed6fc2c852840cba0ed4fafda2fc3875b22bb3a" } } ], "extra": [ 1, 41, 77, 159, 70, 248, 7, 173, 116, 72, 213, 153, 146, 204, 236, 192, 251, 85, 212, 187, 19, 191, 41, 64, 218, 14, 110, 227, 30, 42, 45, 220, 29, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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