Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31921182d8aff6bc6c67925de3cd3dfbd1df17b5779b9085403d063f550d2d8

Tx prefix hash: 9929112f63aa8d58e4bce0991506be7133eeaf7899877c1faeb3628971413884
Tx public key: d2b40a7f036cf5bff1648bf91797710ee4a5c85908a627f991dc53d8b9182f8a
Timestamp: 1770596147 Timestamp [UTC]: 2026-02-09 00:15:47 Age [y:d:h:m:s]: 00:278:10:39:09
Block: 1473713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204378 RingCT/type: yes/0
Extra: 01d2b40a7f036cf5bff1648bf91797710ee4a5c85908a627f991dc53d8b9182f8a021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 963d3e42ea48c5f71403e0ae4bbe6975e997a44fd4f58c2a5432ecef320ab6ab 0.000600000000 1963003 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 dinastycoin-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": 1473723, "vin": [ { "gen": { "height": 1473713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "963d3e42ea48c5f71403e0ae4bbe6975e997a44fd4f58c2a5432ecef320ab6ab" } } ], "extra": [ 1, 210, 180, 10, 127, 3, 108, 245, 191, 241, 100, 139, 249, 23, 151, 113, 14, 228, 165, 200, 89, 8, 166, 39, 249, 145, 220, 83, 216, 185, 24, 47, 138, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: