Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5422524499764dcc181a4c72be271a020d7c5c443b6acfe6cc185ac40e8debad

Tx prefix hash: dcfbc87a0b2e793c6bd7767181952944f8fcdc9830782e4a25ec3c5fd7646369
Tx public key: 6f79f54db08c9cee1c4dc72df91058547d552b049b9943b822e6c1926f4a3905
Timestamp: 1725521600 Timestamp [UCT]: 2024-09-05 07:33:20 Age [y:d:h:m:s]: 00:193:04:04:17
Block: 1103333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137915 RingCT/type: yes/0
Extra: 016f79f54db08c9cee1c4dc72df91058547d552b049b9943b822e6c1926f4a390502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65ce9cf25a888b562a724592576a0c985a10b149eb2e5c078062bdda0e344b38 0.600000000000 1580120 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": 1103343, "vin": [ { "gen": { "height": 1103333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65ce9cf25a888b562a724592576a0c985a10b149eb2e5c078062bdda0e344b38" } } ], "extra": [ 1, 111, 121, 245, 77, 176, 140, 156, 238, 28, 77, 199, 45, 249, 16, 88, 84, 125, 85, 43, 4, 155, 153, 67, 184, 34, 230, 193, 146, 111, 74, 57, 5, 2, 17, 0, 0, 0, 6, 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