Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890aeda01c90863e519e930332002f633e841cdc6d167b844e6ebbc4c7ecae68

Tx prefix hash: 17a2cbb178aa65530510126a7d4f1561c1a3a7cb69b4a4dbc0f4c15b87e879e7
Tx public key: 5b6ee893aee883f72fbe07b95ced77dc05632c4b06748ba578ff4eb120b6e6ef
Timestamp: 1771130665 Timestamp [UTC]: 2026-02-15 04:44:25 Age [y:d:h:m:s]: 00:272:23:43:28
Block: 1478099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200538 RingCT/type: yes/0
Extra: 015b6ee893aee883f72fbe07b95ced77dc05632c4b06748ba578ff4eb120b6e6ef021100000009f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96d2642a87109ff8eef0c3a4a11dc4fdfbc4023f10e40e9fa52cf3704a2e6069 0.000600000000 1967423 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": 1478109, "vin": [ { "gen": { "height": 1478099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96d2642a87109ff8eef0c3a4a11dc4fdfbc4023f10e40e9fa52cf3704a2e6069" } } ], "extra": [ 1, 91, 110, 232, 147, 174, 232, 131, 247, 47, 190, 7, 185, 92, 237, 119, 220, 5, 99, 44, 75, 6, 116, 139, 165, 120, 255, 78, 177, 32, 182, 230, 239, 2, 17, 0, 0, 0, 9, 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: