Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6be37c445afdbf1cd3a020b684706422fca6ed9760b32765d24f9e823bd2636f

Tx prefix hash: 970636b98760aae9fb5a461e732128de05df289252bc8f4bfaec6a6ee914dc41
Tx public key: a7513c5b82cfe84b6689c2ba13aec567ca191b9cccc0b2e4bf5d8dc64bcfd30e
Timestamp: 1685816020 Timestamp [UCT]: 2023-06-03 18:13:40 Age [y:d:h:m:s]: 01:293:18:15:17
Block: 774394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471155 RingCT/type: yes/0
Extra: 01a7513c5b82cfe84b6689c2ba13aec567ca191b9cccc0b2e4bf5d8dc64bcfd30e02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.667674850000 dcy

stealth address amount amount idx
00: 96fb20bd915c77a38166bf531f34e0fd5a162361e8e8aa936d0dba676849275f 1.667674850000 1223869 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": 774404, "vin": [ { "gen": { "height": 774394 } } ], "vout": [ { "amount": 1667674850, "target": { "key": "96fb20bd915c77a38166bf531f34e0fd5a162361e8e8aa936d0dba676849275f" } } ], "extra": [ 1, 167, 81, 60, 91, 130, 207, 232, 75, 102, 137, 194, 186, 19, 174, 197, 103, 202, 25, 27, 156, 204, 192, 178, 228, 191, 93, 141, 198, 75, 207, 211, 14, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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