Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49047bc786a84dc321b25fa149fe757a182b6807f9d60d5fd7b6cf3279b8729d

Tx prefix hash: 5ca1fdfd51eb6e4589af100f3d5bd5d53d9f06d234f068d983418ab629f4b606
Tx public key: 55cf65414745d21ce2a8feb002009003e5ca7a0e969b9a6145e3b34499874a9c
Timestamp: 1721291534 Timestamp [UCT]: 2024-07-18 08:32:14 Age [y:d:h:m:s]: 00:220:02:48:40
Block: 1068273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157189 RingCT/type: yes/0
Extra: 0155cf65414745d21ce2a8feb002009003e5ca7a0e969b9a6145e3b34499874a9c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8b2501b58c880fec6d26dd56b3d17a959d916f5359e94d40131ba28d6f66509 0.600000000000 1539350 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": 1068283, "vin": [ { "gen": { "height": 1068273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8b2501b58c880fec6d26dd56b3d17a959d916f5359e94d40131ba28d6f66509" } } ], "extra": [ 1, 85, 207, 101, 65, 71, 69, 210, 28, 226, 168, 254, 176, 2, 0, 144, 3, 229, 202, 122, 14, 150, 155, 154, 97, 69, 227, 179, 68, 153, 135, 74, 156, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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