Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85209b041470f63c23024d716389862ac6dcaf94f98583b7a7ac82b5a2da7d0

Tx prefix hash: 75fe2e289b17fb508d0df7fcdca9a2c284543501dd73b285f7211fecc03e485a
Tx public key: faf7dfb32b8c4490484715c67120e5ddb9b062b1bc2cea7bb2c94bbedb11bd63
Timestamp: 1740293854 Timestamp [UCT]: 2025-02-23 06:57:34 Age [y:d:h:m:s]: 00:227:00:48:45
Block: 1225321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159982 RingCT/type: yes/0
Extra: 01faf7dfb32b8c4490484715c67120e5ddb9b062b1bc2cea7bb2c94bbedb11bd63021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e98851bf825a06ef2a28e3f2b0a6e28e59ad9c77d607d568a10c41a41425605b 0.600000000000 1712186 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": 1225331, "vin": [ { "gen": { "height": 1225321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e98851bf825a06ef2a28e3f2b0a6e28e59ad9c77d607d568a10c41a41425605b" } } ], "extra": [ 1, 250, 247, 223, 179, 43, 140, 68, 144, 72, 71, 21, 198, 113, 32, 229, 221, 185, 176, 98, 177, 188, 44, 234, 123, 178, 201, 75, 190, 219, 17, 189, 99, 2, 17, 0, 0, 0, 4, 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