Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afbd02e8ee6fa6348db291a82fc4acc4b7adb597d65ddedae8a43d39d0865252

Tx prefix hash: 6da2227c14c024d16f5b768b87d85cd8010f1cd89a6dc0ad118e7ba6d66abe36
Tx public key: b6629229416ff7139816684c1e925186106c494572b935091ff6c0d0f2c3bfcd
Timestamp: 1773251859 Timestamp [UTC]: 2026-03-11 17:57:39 Age [y:d:h:m:s]: 00:252:21:10:18
Block: 1495660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186307 RingCT/type: yes/0
Extra: 01b6629229416ff7139816684c1e925186106c494572b935091ff6c0d0f2c3bfcd021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 274a015e716e9ee723a460fd02f4c1aa2571057754d60335262fb80ad97154ea 0.000600000000 1985274 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": 1495670, "vin": [ { "gen": { "height": 1495660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "274a015e716e9ee723a460fd02f4c1aa2571057754d60335262fb80ad97154ea" } } ], "extra": [ 1, 182, 98, 146, 41, 65, 111, 247, 19, 152, 22, 104, 76, 30, 146, 81, 134, 16, 108, 73, 69, 114, 185, 53, 9, 31, 246, 192, 208, 242, 195, 191, 205, 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: