Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9476d2f0dd3cd8a66228724cfcb393646779d4cf2abca832c9ec05c8496837b

Tx prefix hash: 750479614cf396191d49eea8ad51975652521301896b4c6b8806eff4da60db4f
Tx public key: e1aff30d4bdf8bc7fc8298d047b424a66e86daaea35856a01b2481e59b4804e2
Timestamp: 1752410411 Timestamp [UCT]: 2025-07-13 12:40:11 Age [y:d:h:m:s]: 00:086:19:11:36
Block: 1324604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60702 RingCT/type: yes/0
Extra: 01e1aff30d4bdf8bc7fc8298d047b424a66e86daaea35856a01b2481e59b4804e2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b210a9b2469b2a3952c1c3e4e2b29832dbc38bf5db9c9e616c40dc9a40a897a3 0.600000000000 1812347 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": 1324614, "vin": [ { "gen": { "height": 1324604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b210a9b2469b2a3952c1c3e4e2b29832dbc38bf5db9c9e616c40dc9a40a897a3" } } ], "extra": [ 1, 225, 175, 243, 13, 75, 223, 139, 199, 252, 130, 152, 208, 71, 180, 36, 166, 110, 134, 218, 174, 163, 88, 86, 160, 27, 36, 129, 229, 155, 72, 4, 226, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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