Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a41de8f814e57d2a4960f59218c18e6432a41b78853d163f466dd960bb4e0618

Tx prefix hash: 183d9c68088560d5c5e485b017a35f44916e8f764f51914984e5a74ef051a394
Tx public key: 1f04f23d9a16c14601252426e1b36dee0b734610892df673df17cc469452aadd
Timestamp: 1742582458 Timestamp [UTC]: 2025-03-21 18:40:58 Age [y:d:h:m:s]: 01:056:18:03:35
Block: 1244295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291589 RingCT/type: yes/0
Extra: 011f04f23d9a16c14601252426e1b36dee0b734610892df673df17cc469452aadd02110000000458cb2e2b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b67ca49b2ea151d655c8e23d1b6d68ebe00f62cf07417ca2da3c30c6dfcdb331 0.000600000000 1731286 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": 1244305, "vin": [ { "gen": { "height": 1244295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67ca49b2ea151d655c8e23d1b6d68ebe00f62cf07417ca2da3c30c6dfcdb331" } } ], "extra": [ 1, 31, 4, 242, 61, 154, 22, 193, 70, 1, 37, 36, 38, 225, 179, 109, 238, 11, 115, 70, 16, 137, 45, 246, 115, 223, 23, 204, 70, 148, 82, 170, 221, 2, 17, 0, 0, 0, 4, 88, 203, 46, 43, 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: