Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e499d84b3a1db13e76c430cffbc10e1ee0c4cfb19d7f555d0d960cb1714d1c

Tx prefix hash: ea018d7c9b378429f23ea1d8de56a732d1768b08bf2c1112bbf11572310ff714
Tx public key: 86885c88d691e5eea2ae627e1d80cfac2f28d59247d98755c46baad986f312c0
Timestamp: 1759198430 Timestamp [UCT]: 2025-09-30 02:13:50 Age [y:d:h:m:s]: 00:099:08:26:36
Block: 1379407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71148 RingCT/type: yes/0
Extra: 0186885c88d691e5eea2ae627e1d80cfac2f28d59247d98755c46baad986f312c002110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9fdbceb395c0258b15c2676fe5f13f3e17108dc928f516c111028781cd9b0a1 0.600000000000 1867504 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": 1379417, "vin": [ { "gen": { "height": 1379407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9fdbceb395c0258b15c2676fe5f13f3e17108dc928f516c111028781cd9b0a1" } } ], "extra": [ 1, 134, 136, 92, 136, 214, 145, 229, 238, 162, 174, 98, 126, 29, 128, 207, 172, 47, 40, 213, 146, 71, 217, 135, 85, 196, 107, 170, 217, 134, 243, 18, 192, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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