Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b127794e97e4367cda1e8a5f697c790894487ae364c511a65669ba46ea5c32a3

Tx prefix hash: b0d2f452d6c36ee475b701b7da1bf7e3281c40218cbeecc5c980dc8691e89e47
Tx public key: 8a46f1789c2ee766d7f2d2f0eb729bd0d6bb1a908b56395333694b8f3a051bf0
Timestamp: 1750438823 Timestamp [UCT]: 2025-06-20 17:00:23 Age [y:d:h:m:s]: 00:153:00:26:58
Block: 1309180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107198 RingCT/type: yes/0
Extra: 018a46f1789c2ee766d7f2d2f0eb729bd0d6bb1a908b56395333694b8f3a051bf0021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b8ddda33a3d2f24e51ecb0b424ece6aa8a163b4b3b641a287fdb9957b4ebdb5 0.600000000000 1796795 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": 1309190, "vin": [ { "gen": { "height": 1309180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b8ddda33a3d2f24e51ecb0b424ece6aa8a163b4b3b641a287fdb9957b4ebdb5" } } ], "extra": [ 1, 138, 70, 241, 120, 156, 46, 231, 102, 215, 242, 210, 240, 235, 114, 155, 208, 214, 187, 26, 144, 139, 86, 57, 83, 51, 105, 75, 143, 58, 5, 27, 240, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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