Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966066dab6fb71096c5dad57caf45e9845dacba8d922d125183ffa2b0e41c3b0

Tx prefix hash: e2d1e49eca6706916b6b0691917e83e1dbc2a16cc36c21fdeb1fcc064b48a0bb
Tx public key: ae1f741bd7ca38ff44517b132dbf8221572e9724a82a2ed535407ec6334ea1a5
Timestamp: 1756053120 Timestamp [UCT]: 2025-08-24 16:32:00 Age [y:d:h:m:s]: 00:089:06:50:57
Block: 1353534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63740 RingCT/type: yes/0
Extra: 01ae1f741bd7ca38ff44517b132dbf8221572e9724a82a2ed535407ec6334ea1a50211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0424171bc144fdeb7b9c5c139f3282e9ee576e1c6d1f7806a36c5e25a703a37a 0.600000000000 1841509 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": 1353544, "vin": [ { "gen": { "height": 1353534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0424171bc144fdeb7b9c5c139f3282e9ee576e1c6d1f7806a36c5e25a703a37a" } } ], "extra": [ 1, 174, 31, 116, 27, 215, 202, 56, 255, 68, 81, 123, 19, 45, 191, 130, 33, 87, 46, 151, 36, 168, 42, 46, 213, 53, 64, 126, 198, 51, 78, 161, 165, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 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