Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985ee5155f1bee4126ecfba7ecb164b5b273ccd04f9266be6019c2395c9b0ad1

Tx prefix hash: a31495733aba80e15b0bddb7de2e5233b73ed266d0b50e8acad54a4dfeea5fb6
Tx public key: 203a45bdadca5df92fd562ae68c2e619a8e4da17adaf8890866b4e49c29829be
Timestamp: 1726885406 Timestamp [UTC]: 2024-09-21 02:23:26 Age [y:d:h:m:s]: 02:058:03:01:01
Block: 1114637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566270 RingCT/type: yes/0
Extra: 01203a45bdadca5df92fd562ae68c2e619a8e4da17adaf8890866b4e49c29829be021100000001e914dd15000000000000000000

1 output(s) for total of 0.000608010000 xmr

stealth address amount amount idx tag
00: 525333e21e1b9d0d533c2644b2c6a0ee790de87f74acb348493e6e1ed91c1aeb 0.000608010000 1594486 of 0 -

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": 1114647, "vin": [ { "gen": { "height": 1114637 } } ], "vout": [ { "amount": 608010000, "target": { "key": "525333e21e1b9d0d533c2644b2c6a0ee790de87f74acb348493e6e1ed91c1aeb" } } ], "extra": [ 1, 32, 58, 69, 189, 173, 202, 93, 249, 47, 213, 98, 174, 104, 194, 230, 25, 168, 228, 218, 23, 173, 175, 136, 144, 134, 107, 78, 73, 194, 152, 41, 190, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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: