Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93793c629ad56544863f5165e5bfb4b60d7f116190fac8dd4f275a4cd36d233d

Tx prefix hash: 1a045082036bfb96f7566d6b26c47bb2ca5abb981b3240d8d08010e57e09bdd0
Tx public key: e9155448ffd2bd85e6faf9bad9c48c41a8fa95a3c51b6dbd41408fb15daf3a9f
Timestamp: 1750851946 Timestamp [UCT]: 2025-06-25 11:45:46 Age [y:d:h:m:s]: 00:147:19:05:08
Block: 1312493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103573 RingCT/type: yes/0
Extra: 01e9155448ffd2bd85e6faf9bad9c48c41a8fa95a3c51b6dbd41408fb15daf3a9f021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b5f241ae60fa39ea765973a832b26af52b2d535566879f5f838d83f71514cde 0.600000000000 1800126 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": 1312503, "vin": [ { "gen": { "height": 1312493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b5f241ae60fa39ea765973a832b26af52b2d535566879f5f838d83f71514cde" } } ], "extra": [ 1, 233, 21, 84, 72, 255, 210, 189, 133, 230, 250, 249, 186, 217, 196, 140, 65, 168, 250, 149, 163, 197, 27, 109, 189, 65, 64, 143, 177, 93, 175, 58, 159, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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