Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 784915fe6dcd96cdddfe2c65b7c857dee880dfe89ef34ddb6f14555a13f567c5

Tx prefix hash: 28d8effe58249ba7c6c838d10ef1152cdc636b77aabd35d6c58b8abfe0b4a2a0
Tx public key: 967cdc1add4d5b736413fb5712bbd07e069932b36429e547196f891c899f09f9
Timestamp: 1732217422 Timestamp [UCT]: 2024-11-21 19:30:22 Age [y:d:h:m:s]: 00:147:10:26:09
Block: 1158739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105205 RingCT/type: yes/0
Extra: 01967cdc1add4d5b736413fb5712bbd07e069932b36429e547196f891c899f09f9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05bce13b0bd73ac442b822f66435aa65abf966b743c69e0c9ad6af79e21ebdbb 0.600000000000 1644368 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": 1158749, "vin": [ { "gen": { "height": 1158739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05bce13b0bd73ac442b822f66435aa65abf966b743c69e0c9ad6af79e21ebdbb" } } ], "extra": [ 1, 150, 124, 220, 26, 221, 77, 91, 115, 100, 19, 251, 87, 18, 187, 208, 126, 6, 153, 50, 179, 100, 41, 229, 71, 25, 111, 137, 28, 137, 159, 9, 249, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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