Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d916992f16b59ef35706bc47fac73a4b8777847b1046a40d031c86ea1e700ad

Tx prefix hash: ead666a509cd4287df7391d313ade072f5b3c0a0b34d7a0084ce41f49a9252a0
Tx public key: 4467148ce68c834dc916088c15e3e1d14f85930219c2d3943f60d183e15b8e58
Timestamp: 1726679363 Timestamp [UCT]: 2024-09-18 17:09:23 Age [y:d:h:m:s]: 00:177:06:14:17
Block: 1112932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126513 RingCT/type: yes/0
Extra: 014467148ce68c834dc916088c15e3e1d14f85930219c2d3943f60d183e15b8e5802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50d2438e97d5c06a6319a186779f3c6be3b4cfc67707222acb610c51dec9093d 0.600000000000 1592427 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": 1112942, "vin": [ { "gen": { "height": 1112932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50d2438e97d5c06a6319a186779f3c6be3b4cfc67707222acb610c51dec9093d" } } ], "extra": [ 1, 68, 103, 20, 140, 230, 140, 131, 77, 201, 22, 8, 140, 21, 227, 225, 209, 79, 133, 147, 2, 25, 194, 211, 148, 63, 96, 209, 131, 225, 91, 142, 88, 2, 17, 0, 0, 0, 5, 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