Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bced5034b351b893cbe7a1599b3c7234e5536de7301ce2042d0021004fb69ca

Tx prefix hash: c89d6335eea299647fca337231f94699fb45a364b874a84db53adf274a64b3dd
Tx public key: 09dc4ddabf3fddd32010c39b956c059f3d4068643f9b3d4e4840e2f6ee281eeb
Timestamp: 1736540019 Timestamp [UCT]: 2025-01-10 20:13:39 Age [y:d:h:m:s]: 00:160:18:40:21
Block: 1194539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114578 RingCT/type: yes/0
Extra: 0109dc4ddabf3fddd32010c39b956c059f3d4068643f9b3d4e4840e2f6ee281eeb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89c2811ce22fbe2762abd8eb7be347e5c575d0266e675d41a17735012cbe63f2 0.600000000000 1681114 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": 1194549, "vin": [ { "gen": { "height": 1194539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89c2811ce22fbe2762abd8eb7be347e5c575d0266e675d41a17735012cbe63f2" } } ], "extra": [ 1, 9, 220, 77, 218, 191, 63, 221, 211, 32, 16, 195, 155, 149, 108, 5, 159, 61, 64, 104, 100, 63, 155, 61, 78, 72, 64, 226, 246, 238, 40, 30, 235, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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