Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ea2a0a28f78910e940ef948e2ec06dd018bddeaf08631a47c15ccf46e4036b

Tx prefix hash: 671e1f231d4824f77d889735d1db9ad3923e67364f483fbae6ec19b25f0658c9
Tx public key: d0134da779cf641630d5a3d34ec3ceadf484085fa3c5fe3473ac1c8b4d2e8cce
Timestamp: 1773871841 Timestamp [UTC]: 2026-03-18 22:10:41 Age [y:d:h:m:s]: 00:241:22:14:15
Block: 1500775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178366 RingCT/type: yes/0
Extra: 01d0134da779cf641630d5a3d34ec3ceadf484085fa3c5fe3473ac1c8b4d2e8cce02110000000ef188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f8344b0f768dccf6a0efb3e98bfb4a7bc252d6d5d8d5d034deb14611f90db2e4 0.000600000000 1990451 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": 1500785, "vin": [ { "gen": { "height": 1500775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8344b0f768dccf6a0efb3e98bfb4a7bc252d6d5d8d5d034deb14611f90db2e4" } } ], "extra": [ 1, 208, 19, 77, 167, 121, 207, 100, 22, 48, 213, 163, 211, 78, 195, 206, 173, 244, 132, 8, 95, 163, 197, 254, 52, 115, 172, 28, 139, 77, 46, 140, 206, 2, 17, 0, 0, 0, 14, 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: