Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d4a2e50755afa808d201ea2ed62f34322ae2a88bbe1745c16e03d25625b18e

Tx prefix hash: 1d8e58351a7b0cdc0117e3bdd61f7dd0a1e4b9051645d6c2ffb4e243880fe77d
Tx public key: 9a8db6a0c3061b6066296235f9ffb32dbf2f803ed66c7830e8ce5569abef652a
Timestamp: 1716553604 Timestamp [UCT]: 2024-05-24 12:26:44 Age [y:d:h:m:s]: 00:296:13:24:56
Block: 1029002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211943 RingCT/type: yes/0
Extra: 019a8db6a0c3061b6066296235f9ffb32dbf2f803ed66c7830e8ce5569abef652a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5ede1864e30341e2877d4fa12c5202d6bae0cd3b1184b843dee4278ff8b1f47 0.600000000000 1497003 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": 1029012, "vin": [ { "gen": { "height": 1029002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5ede1864e30341e2877d4fa12c5202d6bae0cd3b1184b843dee4278ff8b1f47" } } ], "extra": [ 1, 154, 141, 182, 160, 195, 6, 27, 96, 102, 41, 98, 53, 249, 255, 179, 45, 191, 47, 128, 62, 214, 108, 120, 48, 232, 206, 85, 105, 171, 239, 101, 42, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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