Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d860bc516676ac533127ba7c99f26fba6f04802a09857fea68e1ca389fd05b3c

Tx prefix hash: ee68723ea011c38b5310c444ab45761c5e7febc80c70c6f47b43e7ed2adf84ed
Tx public key: 3fb1f8a054e4f0578cce14fa165cddfb16c6aac83bb1fc12e623a51e424b5d84
Timestamp: 1698410093 Timestamp [UCT]: 2023-10-27 12:34:53 Age [y:d:h:m:s]: 01:146:23:43:32
Block: 878784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366041 RingCT/type: yes/0
Extra: 013fb1f8a054e4f0578cce14fa165cddfb16c6aac83bb1fc12e623a51e424b5d84021100000003faf35c9c000000000000000000

1 output(s) for total of 0.752010357000 dcy

stealth address amount amount idx
00: b60ebcfcfd74013f0cc1aaac77d5876e0a2fca80b44cf2eb5e7b9264468b6b77 0.752010357000 1334262 of 0

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": 878794, "vin": [ { "gen": { "height": 878784 } } ], "vout": [ { "amount": 752010357, "target": { "key": "b60ebcfcfd74013f0cc1aaac77d5876e0a2fca80b44cf2eb5e7b9264468b6b77" } } ], "extra": [ 1, 63, 177, 248, 160, 84, 228, 240, 87, 140, 206, 20, 250, 22, 92, 221, 251, 22, 198, 170, 200, 59, 177, 252, 18, 230, 35, 165, 30, 66, 75, 93, 132, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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