Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ef8782680a5524c48e5ad9d6b68d89921ff1ada5bbf13d20d4bb080c8ca21c

Tx prefix hash: 3cd375146d82da79a9de93dd9f4e3be5d9b864febf2fa212062ded5ac16f0bce
Tx public key: 427e9418cb725f22984e34caed87bcb6de50466b3c504da6e1094f13b250a14c
Timestamp: 1710200400 Timestamp [UCT]: 2024-03-11 23:40:00 Age [y:d:h:m:s]: 01:041:18:47:40
Block: 976321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290854 RingCT/type: yes/0
Extra: 01427e9418cb725f22984e34caed87bcb6de50466b3c504da6e1094f13b250a14c02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e32f006bf7f2e44d1223435b4b0ea32c0e0f87117eb265b6d4a2aa8d1cde1a9e 0.600000000000 1436314 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": 976331, "vin": [ { "gen": { "height": 976321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e32f006bf7f2e44d1223435b4b0ea32c0e0f87117eb265b6d4a2aa8d1cde1a9e" } } ], "extra": [ 1, 66, 126, 148, 24, 203, 114, 95, 34, 152, 78, 52, 202, 237, 135, 188, 182, 222, 80, 70, 107, 60, 80, 77, 166, 225, 9, 79, 19, 178, 80, 161, 76, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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