Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bfa3fb191dd28beefd9b5e72850f4dd1820134501d09d07a66861f9d81b5bfd

Tx prefix hash: 05eeb263ed08bf76cb488b62931f911460e865a65e51600925d27df2d8c45f9f
Tx public key: 490c352a4b720f06bd74d965b0fc16f439aab3dbdcc928d0c81e9d0b2ae43ee2
Timestamp: 1760996151 Timestamp [UCT]: 2025-10-20 21:35:51 Age [y:d:h:m:s]: 00:099:17:21:27
Block: 1394339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71200 RingCT/type: yes/0
Extra: 01490c352a4b720f06bd74d965b0fc16f439aab3dbdcc928d0c81e9d0b2ae43ee20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6b875e10958bd5bd1c3ef123c7bf125e05bbe2c7af5697d085bc3bde1384f2d 0.600000000000 1882610 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": 1394349, "vin": [ { "gen": { "height": 1394339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6b875e10958bd5bd1c3ef123c7bf125e05bbe2c7af5697d085bc3bde1384f2d" } } ], "extra": [ 1, 73, 12, 53, 42, 75, 114, 15, 6, 189, 116, 217, 101, 176, 252, 22, 244, 57, 170, 179, 219, 220, 201, 40, 208, 200, 30, 157, 11, 42, 228, 62, 226, 2, 17, 0, 0, 0, 1, 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