Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0cd81bbb348f8cf9bd51c172e9440b20ee419502ba68326dce62d693e0e0c67

Tx prefix hash: 245f403ea178ad194afc15239fdbafbeb97198351f9df423a719d3581db5b906
Tx public key: 5d5b32868e18e63da1ffa5d41bf1124ef0e2afe3b3f6d5cc6ca80b947983c9f3
Timestamp: 1738397734 Timestamp [UCT]: 2025-02-01 08:15:34 Age [y:d:h:m:s]: 00:292:14:12:25
Block: 1209647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206883 RingCT/type: yes/0
Extra: 015d5b32868e18e63da1ffa5d41bf1124ef0e2afe3b3f6d5cc6ca80b947983c9f3021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 774650e9fbe01f72a1881fb6464bd435de3c104d697d113d5a96b8c5467798d0 0.600000000000 1696392 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": 1209657, "vin": [ { "gen": { "height": 1209647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "774650e9fbe01f72a1881fb6464bd435de3c104d697d113d5a96b8c5467798d0" } } ], "extra": [ 1, 93, 91, 50, 134, 142, 24, 230, 61, 161, 255, 165, 212, 27, 241, 18, 78, 240, 226, 175, 227, 179, 246, 213, 204, 108, 168, 11, 148, 121, 131, 201, 243, 2, 17, 0, 0, 0, 5, 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