Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d505ef8a72399e1acd0d5bcb4b43af84c09a271655044ae9e4af824e3fb49db

Tx prefix hash: c163a0ff387c97e266123edafb1e6977e0df69b410a61885f9c14431e722bb98
Tx public key: e614ce00bdeb91dc97e072da8b423a4dbc363f49ab357770ab82d7d1ebf89c23
Timestamp: 1703548724 Timestamp [UCT]: 2023-12-25 23:58:44 Age [y:d:h:m:s]: 01:113:20:28:02
Block: 921166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342484 RingCT/type: yes/0
Extra: 01e614ce00bdeb91dc97e072da8b423a4dbc363f49ab357770ab82d7d1ebf89c2302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf3e1c45ef9b7cf6cc8bc97fbee5e9ed3ad288a1239464dd1f3775d4cccf59be 0.600000000000 1378850 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": 921176, "vin": [ { "gen": { "height": 921166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf3e1c45ef9b7cf6cc8bc97fbee5e9ed3ad288a1239464dd1f3775d4cccf59be" } } ], "extra": [ 1, 230, 20, 206, 0, 189, 235, 145, 220, 151, 224, 114, 218, 139, 66, 58, 77, 188, 54, 63, 73, 171, 53, 119, 112, 171, 130, 215, 209, 235, 248, 156, 35, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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