Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8cabc2f081bb64b20368c5273e67b5049bcfdaa9b322f279ba201d266a6b1c

Tx prefix hash: a67eedffbb44c8e5e66258c75ed79908219aa3f49552fdb28e7e21f59515350d
Tx public key: abefe8f466172a7d8a26e526488b7f7b1dacce9b0909d0e50416e9af0cbc284a
Timestamp: 1744140772 Timestamp [UTC]: 2025-04-08 19:32:52 Age [y:d:h:m:s]: 01:036:08:28:05
Block: 1257184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276906 RingCT/type: yes/0
Extra: 01abefe8f466172a7d8a26e526488b7f7b1dacce9b0909d0e50416e9af0cbc284a0211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0c213a6701b3b4e7ce3fb2c775be09df74982d522506bc8676804c66bdecd3eb 0.000600000000 1744303 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": 1257194, "vin": [ { "gen": { "height": 1257184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c213a6701b3b4e7ce3fb2c775be09df74982d522506bc8676804c66bdecd3eb" } } ], "extra": [ 1, 171, 239, 232, 244, 102, 23, 42, 125, 138, 38, 229, 38, 72, 139, 127, 123, 29, 172, 206, 155, 9, 9, 208, 229, 4, 22, 233, 175, 12, 188, 40, 74, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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: