Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8b9694e34f159ff837c5dd8c36d8a811bf7db2e167c624f4d05e50ba7d4af3e

Tx prefix hash: c67b296ad74dd978a9893a01160ad53bb98584ae638ffd5a9e6d1cdd3152f03d
Tx public key: 5a8a037095fcd3c59c0d29c3c12f1dd3cd1cf7a1f89481e6f240225a00b1140e
Timestamp: 1773890976 Timestamp [UTC]: 2026-03-19 03:29:36 Age [y:d:h:m:s]: 00:245:17:00:33
Block: 1500931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181211 RingCT/type: yes/0
Extra: 015a8a037095fcd3c59c0d29c3c12f1dd3cd1cf7a1f89481e6f240225a00b1140e021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 178bcf61af88ad93264787c2028a731f9e84da9ac90ee2d17bcdd1306c3bf673 0.000600000000 1990609 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": 1500941, "vin": [ { "gen": { "height": 1500931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "178bcf61af88ad93264787c2028a731f9e84da9ac90ee2d17bcdd1306c3bf673" } } ], "extra": [ 1, 90, 138, 3, 112, 149, 252, 211, 197, 156, 13, 41, 195, 193, 47, 29, 211, 205, 28, 247, 161, 248, 148, 129, 230, 242, 64, 34, 90, 0, 177, 20, 14, 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: