Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 238746b4c5a7a855ce44083d0cfd94035ca4e3e908baada1785770cb0937e8b9

Tx prefix hash: f9afa3bac5c6b69656ebbbc4277ac4010b2f366f8992f1479fbd4b67ed5d7aeb
Tx public key: b2d583158ff0f8d54bc1f10b2df2f82dc7885f3de4ef0c67881c7c63cff1c889
Timestamp: 1774104195 Timestamp [UTC]: 2026-03-21 14:43:15 Age [y:d:h:m:s]: 00:239:06:43:11
Block: 1502691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176481 RingCT/type: yes/0
Extra: 01b2d583158ff0f8d54bc1f10b2df2f82dc7885f3de4ef0c67881c7c63cff1c889021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96be0bda2e80f7c0e32dcc2db20421f629ad62f579552ca020259297474a57e2 0.000600000000 1992393 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": 1502701, "vin": [ { "gen": { "height": 1502691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96be0bda2e80f7c0e32dcc2db20421f629ad62f579552ca020259297474a57e2" } } ], "extra": [ 1, 178, 213, 131, 21, 143, 240, 248, 213, 75, 193, 241, 11, 45, 242, 248, 45, 199, 136, 95, 61, 228, 239, 12, 103, 136, 28, 124, 99, 207, 241, 200, 137, 2, 17, 0, 0, 0, 7, 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: