Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63efebcdcb9f1f34f71245317cc80fbd3b7afa612fe5a875bab47843ffb37c10

Tx prefix hash: 340984c855c20d63cb00d4c79cfb4178004f73f602d7df803d8b3dbe4d141b17
Tx public key: 26ad8d1599b2c382f71fdc995eff6d78e9376aa830eda0bd66ed32cdf46c8759
Timestamp: 1749692885 Timestamp [UCT]: 2025-06-12 01:48:05 Age [y:d:h:m:s]: 00:151:19:46:17
Block: 1303142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106209 RingCT/type: yes/0
Extra: 0126ad8d1599b2c382f71fdc995eff6d78e9376aa830eda0bd66ed32cdf46c875902110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80e4df21437a94d7532fd7969e44e1bef03adb81735f13cc64baeaf0c0e0b8c2 0.600000000000 1790717 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": 1303152, "vin": [ { "gen": { "height": 1303142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80e4df21437a94d7532fd7969e44e1bef03adb81735f13cc64baeaf0c0e0b8c2" } } ], "extra": [ 1, 38, 173, 141, 21, 153, 178, 195, 130, 247, 31, 220, 153, 94, 255, 109, 120, 233, 55, 106, 168, 48, 237, 160, 189, 102, 237, 50, 205, 244, 108, 135, 89, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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