Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a37a999646c0b8621e5ea1fbbd65093e17c34debafb80d3a1775aa11c319bc0

Tx prefix hash: b3245f4a4c8c6a2c05b958b060c9451c4859148d70d73b47d3d9e9a8944443e9
Tx public key: 93706e893c46c97f0edf6c6821f7bd19a55851a2dbb55916661b53e553113041
Timestamp: 1741238803 Timestamp [UCT]: 2025-03-06 05:26:43 Age [y:d:h:m:s]: 00:006:12:11:22
Block: 1233174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4667 RingCT/type: yes/0
Extra: 0193706e893c46c97f0edf6c6821f7bd19a55851a2dbb55916661b53e553113041021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1cb8e0bfb6bfefc20f80451f801fc0ab6324a873b9848cfa5b27b9c76acae5 0.600000000000 1720093 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": 1233184, "vin": [ { "gen": { "height": 1233174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1cb8e0bfb6bfefc20f80451f801fc0ab6324a873b9848cfa5b27b9c76acae5" } } ], "extra": [ 1, 147, 112, 110, 137, 60, 70, 201, 127, 14, 223, 108, 104, 33, 247, 189, 25, 165, 88, 81, 162, 219, 181, 89, 22, 102, 27, 83, 229, 83, 17, 48, 65, 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