Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f70b0b105e13942cbadf6f6e0a69b6928c224faf1dd98305cc92ea20eb765460

Tx prefix hash: 2281477623702bdb45a37a3f6fea96eaf7b0e997a7f2fa21af6ea2dc001c355c
Tx public key: bf05350598402058a4b38f0310f1166a5c39ee4b914bc7d5cfc95cdb117cc421
Timestamp: 1750071795 Timestamp [UCT]: 2025-06-16 11:03:15 Age [y:d:h:m:s]: 00:146:05:30:42
Block: 1306187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102305 RingCT/type: yes/0
Extra: 01bf05350598402058a4b38f0310f1166a5c39ee4b914bc7d5cfc95cdb117cc421021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46fdc6e927e692402e8ece1a4ef8ca88ff2505e5e683e8ec95ad4c8a5df0b8df 0.600000000000 1793790 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": 1306197, "vin": [ { "gen": { "height": 1306187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46fdc6e927e692402e8ece1a4ef8ca88ff2505e5e683e8ec95ad4c8a5df0b8df" } } ], "extra": [ 1, 191, 5, 53, 5, 152, 64, 32, 88, 164, 179, 143, 3, 16, 241, 22, 106, 92, 57, 238, 75, 145, 75, 199, 213, 207, 201, 92, 219, 17, 124, 196, 33, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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