Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6da5ee25957753be01321d9060d27cf2031347fee5bb9c05fa88491d0c47dc5

Tx prefix hash: 1e6b3c31771d6707beb14bfcff314655b883af239d77798e0f953e795d9c905e
Tx public key: 675e21fa8efa28e4b824152f7bf3f20505abfa28e1d835da0954aec11fe4d947
Timestamp: 1695480232 Timestamp [UCT]: 2023-09-23 14:43:52 Age [y:d:h:m:s]: 01:202:22:14:49
Block: 854474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406104 RingCT/type: yes/0
Extra: 01675e21fa8efa28e4b824152f7bf3f20505abfa28e1d835da0954aec11fe4d9470211000000044b8f5122000000000000000000

1 output(s) for total of 0.905259266000 dcy

stealth address amount amount idx
00: 7776bcef9e62cd7fe6b97e127da602e2ca7e49dfedba18912ebb08a3cc7f1c12 0.905259266000 1308448 of 0

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": 854484, "vin": [ { "gen": { "height": 854474 } } ], "vout": [ { "amount": 905259266, "target": { "key": "7776bcef9e62cd7fe6b97e127da602e2ca7e49dfedba18912ebb08a3cc7f1c12" } } ], "extra": [ 1, 103, 94, 33, 250, 142, 250, 40, 228, 184, 36, 21, 47, 123, 243, 242, 5, 5, 171, 250, 40, 225, 216, 53, 218, 9, 84, 174, 193, 31, 228, 217, 71, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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