Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c997470e7b3a753085c0d71cd6ade3f1162302ce3b02278fcf7fa9aaca345c92

Tx prefix hash: f9986451bbdb21f84bc17c3f060055e2749628f1462e5dc881d645d4038289fc
Tx public key: 13579d8179cdbcc80e8d14fba157d2b98a3fecc4e4a48dbc82a56a330eac07d1
Timestamp: 1746208133 Timestamp [UTC]: 2025-05-02 17:48:53 Age [y:d:h:m:s]: 01:013:18:10:43
Block: 1274308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260767 RingCT/type: yes/0
Extra: 0113579d8179cdbcc80e8d14fba157d2b98a3fecc4e4a48dbc82a56a330eac07d10211000000049f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e686af0f46d5285fa0391516adfdf49654a8d39ef514bf0f76ae9c0a8f6c6294 0.000600000000 1761603 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": 1274318, "vin": [ { "gen": { "height": 1274308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e686af0f46d5285fa0391516adfdf49654a8d39ef514bf0f76ae9c0a8f6c6294" } } ], "extra": [ 1, 19, 87, 157, 129, 121, 205, 188, 200, 14, 141, 20, 251, 161, 87, 210, 185, 138, 63, 236, 196, 228, 164, 141, 188, 130, 165, 106, 51, 14, 172, 7, 209, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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: