Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9caddb2bd01b5ed38d1bdbf2446e9d417e511ec14c9c78feab8168e83f716a1

Tx prefix hash: 7d0e40ff951d56711cdcb290728253fc614c1acb3afae93c62341147e7c85319
Tx public key: fab5ea7d2b391d74f6b580f94dc779eca199ae5dea024f9af361e32ad20923f0
Timestamp: 1712593028 Timestamp [UTC]: 2024-04-08 16:17:08 Age [y:d:h:m:s]: 02:035:23:49:13
Block: 996112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537599 RingCT/type: yes/0
Extra: 01fab5ea7d2b391d74f6b580f94dc779eca199ae5dea024f9af361e32ad20923f002110000000159dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 68425b97ace2430d13f1baaa27681b10688ba40d33902fa1d7a4fbff7d125cb9 0.000600000000 1456528 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": 996122, "vin": [ { "gen": { "height": 996112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68425b97ace2430d13f1baaa27681b10688ba40d33902fa1d7a4fbff7d125cb9" } } ], "extra": [ 1, 250, 181, 234, 125, 43, 57, 29, 116, 246, 181, 128, 249, 77, 199, 121, 236, 161, 153, 174, 93, 234, 2, 79, 154, 243, 97, 227, 42, 210, 9, 35, 240, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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: