Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 900a9a8789d0b35f9eafa3b545044469097a2e1ffae85b6923e421961828e111

Tx prefix hash: 23be9ff1aca5bab1a3051347b64e694b1505b7be0cfbf35298ae252a36225d10
Tx public key: 636c96c11812c95674cb61f3f1138533ae4f0416038c610193f7f7bc616e21cd
Timestamp: 1759109899 Timestamp [UCT]: 2025-09-29 01:38:19 Age [y:d:h:m:s]: 00:042:19:56:03
Block: 1378674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30677 RingCT/type: yes/0
Extra: 01636c96c11812c95674cb61f3f1138533ae4f0416038c610193f7f7bc616e21cd021100000006a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ac1e575c0f51d1d74fa6c620a04fd7566fe0d40566e2caf8b732f6f4d4b4ef4 0.600000000000 1866769 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": 1378684, "vin": [ { "gen": { "height": 1378674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ac1e575c0f51d1d74fa6c620a04fd7566fe0d40566e2caf8b732f6f4d4b4ef4" } } ], "extra": [ 1, 99, 108, 150, 193, 24, 18, 201, 86, 116, 203, 97, 243, 241, 19, 133, 51, 174, 79, 4, 22, 3, 140, 97, 1, 147, 247, 247, 188, 97, 110, 33, 205, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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