Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dde8e7adb3d5234691c6fa00feaa675d5cb8ac23fe2e25506041540da8e60f3

Tx prefix hash: 0c77628509b9c8d86ab8ede6a2564500c00ad42ece82f0e1bbce5b9c473b6d73
Tx public key: f2a702ba9e8c0dad78bf60cbc78b6a0bc30de9a888aa1004b9dfb5a4be5e58a6
Timestamp: 1719165692 Timestamp [UCT]: 2024-06-23 18:01:32 Age [y:d:h:m:s]: 00:292:08:12:38
Block: 1050620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208927 RingCT/type: yes/0
Extra: 01f2a702ba9e8c0dad78bf60cbc78b6a0bc30de9a888aa1004b9dfb5a4be5e58a60211000000030fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c76eb135b43bcb5b930d4c94186b873cd0e2fc85f5308305c6a2471e30b129bd 0.600000000000 1520795 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": 1050630, "vin": [ { "gen": { "height": 1050620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c76eb135b43bcb5b930d4c94186b873cd0e2fc85f5308305c6a2471e30b129bd" } } ], "extra": [ 1, 242, 167, 2, 186, 158, 140, 13, 173, 120, 191, 96, 203, 199, 139, 106, 11, 195, 13, 233, 168, 136, 170, 16, 4, 185, 223, 181, 164, 190, 94, 88, 166, 2, 17, 0, 0, 0, 3, 15, 187, 196, 197, 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