Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc2eb3ea08b811ff7969e47b01390a29db2c74431fdb9dfd8a756f66f9e66bdf

Tx prefix hash: 2cfaeee156e69ac294210c973b9bb4aaf0174514411497ef70724ac4e216de39
Tx public key: aef7cc714f9f072295b7e838195a16db58df4ae41f406fe3ea791ff4088314cb
Timestamp: 1736458284 Timestamp [UCT]: 2025-01-09 21:31:24 Age [y:d:h:m:s]: 00:075:00:28:47
Block: 1193865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53390 RingCT/type: yes/0
Extra: 01aef7cc714f9f072295b7e838195a16db58df4ae41f406fe3ea791ff4088314cb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e1f9aa544691cd32116fbae2a9fd4e4f5a8d5fb45e0a63b341691fb06487ea6 0.600000000000 1680430 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": 1193875, "vin": [ { "gen": { "height": 1193865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e1f9aa544691cd32116fbae2a9fd4e4f5a8d5fb45e0a63b341691fb06487ea6" } } ], "extra": [ 1, 174, 247, 204, 113, 79, 159, 7, 34, 149, 183, 232, 56, 25, 90, 22, 219, 88, 223, 74, 228, 31, 64, 111, 227, 234, 121, 31, 244, 8, 131, 20, 203, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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