Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e847710c6b4cb30bc89c94f34d876e6778c34994a4169744c330f2e7111b5441

Tx prefix hash: ed0420e1475cbe3bb4413660ebf061f8bc92c22ebabe92d35457f0a5d328c72b
Tx public key: 33c528dec41f6de9c0ef7000fc0e629726f8688efcbe61ec1466d0a2f0f3bbf6
Timestamp: 1715531907 Timestamp [UCT]: 2024-05-12 16:38:27 Age [y:d:h:m:s]: 00:288:10:49:58
Block: 1020543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206116 RingCT/type: yes/0
Extra: 0133c528dec41f6de9c0ef7000fc0e629726f8688efcbe61ec1466d0a2f0f3bbf6021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c07f51f17d7d6c651d0550f51a05eae91f688b6a2bfda7d946969876bf73ba91 0.600000000000 1484624 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": 1020553, "vin": [ { "gen": { "height": 1020543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c07f51f17d7d6c651d0550f51a05eae91f688b6a2bfda7d946969876bf73ba91" } } ], "extra": [ 1, 51, 197, 40, 222, 196, 31, 109, 233, 192, 239, 112, 0, 252, 14, 98, 151, 38, 248, 104, 142, 252, 190, 97, 236, 20, 102, 208, 162, 240, 243, 187, 246, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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