Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 606dceec63c7445340f8f412daa62713d5017abbb944ea8e37795b00e85c97e0

Tx prefix hash: fbbf5bc07c8d6ad995d54bc90148be71b9bb4ab21bf5fdb72261ca0a397459b5
Tx public key: fda0339dac0d845ee534a8d2f13efb62dd7595bdb4a2feeb04fbf8233abe0cf6
Timestamp: 1713879890 Timestamp [UCT]: 2024-04-23 13:44:50 Age [y:d:h:m:s]: 00:252:23:32:19
Block: 1006822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181080 RingCT/type: yes/0
Extra: 01fda0339dac0d845ee534a8d2f13efb62dd7595bdb4a2feeb04fbf8233abe0cf60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 909e1ca001b18f1d07850c8e42b9a856df213bed3b50f7e65cc07e272ff5d9d8 0.600000000000 1467966 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": 1006832, "vin": [ { "gen": { "height": 1006822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "909e1ca001b18f1d07850c8e42b9a856df213bed3b50f7e65cc07e272ff5d9d8" } } ], "extra": [ 1, 253, 160, 51, 157, 172, 13, 132, 94, 229, 52, 168, 210, 241, 62, 251, 98, 221, 117, 149, 189, 180, 162, 254, 235, 4, 251, 248, 35, 58, 190, 12, 246, 2, 17, 0, 0, 0, 1, 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