Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16246793cbb85283edec6cea7dab6c1f28b8427dd0b03eea813de4c30272db4d

Tx prefix hash: e537f2962422a2e9463039363481e8fb8e816b936d32478d52d672ac34c7f4e3
Tx public key: e4e75bb6631b86753ef77fe097fee950a91ed9d71ab4d7b2f1d235cbed8bf8dc
Timestamp: 1749695370 Timestamp [UCT]: 2025-06-12 02:29:30 Age [y:d:h:m:s]: 00:160:17:44:30
Block: 1303159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112593 RingCT/type: yes/0
Extra: 01e4e75bb6631b86753ef77fe097fee950a91ed9d71ab4d7b2f1d235cbed8bf8dc02110000000b43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87403f5858c1c7586ec8d8a89985a76b824632ea90ba7a03101b4ea5869a9a20 0.600000000000 1790734 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": 1303169, "vin": [ { "gen": { "height": 1303159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87403f5858c1c7586ec8d8a89985a76b824632ea90ba7a03101b4ea5869a9a20" } } ], "extra": [ 1, 228, 231, 91, 182, 99, 27, 134, 117, 62, 247, 127, 224, 151, 254, 233, 80, 169, 30, 217, 215, 26, 180, 215, 178, 241, 210, 53, 203, 237, 139, 248, 220, 2, 17, 0, 0, 0, 11, 67, 132, 109, 102, 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