Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443d8673707502917bb4f0b13ea351118817b49c59af9797e32da19c8e5f9fb1

Tx prefix hash: 6ab085153d528ba8ecee88ee026645e59361260987151c5262653820a373aaee
Tx public key: eaa1f65e7e0ab233fee6a2e3fca1ed6d6692a17b6d9fff30ddf9ef28a769d92d
Timestamp: 1750347867 Timestamp [UCT]: 2025-06-19 15:44:27 Age [y:d:h:m:s]: 00:147:19:01:55
Block: 1308459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103434 RingCT/type: yes/0
Extra: 01eaa1f65e7e0ab233fee6a2e3fca1ed6d6692a17b6d9fff30ddf9ef28a769d92d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffacf5ce044b06034817dbb098ebddf2f33ef4352c21fe66ebd3c720d253b357 0.600000000000 1796072 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": 1308469, "vin": [ { "gen": { "height": 1308459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffacf5ce044b06034817dbb098ebddf2f33ef4352c21fe66ebd3c720d253b357" } } ], "extra": [ 1, 234, 161, 246, 94, 126, 10, 178, 51, 254, 230, 162, 227, 252, 161, 237, 109, 102, 146, 161, 123, 109, 159, 255, 48, 221, 249, 239, 40, 167, 105, 217, 45, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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