Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2da8e84ca2d06dc0c7da4fcca7773b62dbcf7a162551fd9b92b66a271287635d

Tx prefix hash: 4bdf8352fd0054247ea44203ec34b68d67da0b88d17daebf1e4ad77fe9a88820
Tx public key: 0bb1a82e2f9eb09fc81d4b7d7f76942bb6d5f8ba1f77b24ce4bb66c2200d4f8b
Timestamp: 1732170390 Timestamp [UTC]: 2024-11-21 06:26:30 Age [y:d:h:m:s]: 01:359:16:33:47
Block: 1158352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520868 RingCT/type: yes/0
Extra: 010bb1a82e2f9eb09fc81d4b7d7f76942bb6d5f8ba1f77b24ce4bb66c2200d4f8b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1c68e32690701fa633322e2cbe4f24ceb512de45b0091945b136b8d4608ca1b0 0.000600000000 1643981 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": 1158362, "vin": [ { "gen": { "height": 1158352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c68e32690701fa633322e2cbe4f24ceb512de45b0091945b136b8d4608ca1b0" } } ], "extra": [ 1, 11, 177, 168, 46, 47, 158, 176, 159, 200, 29, 75, 125, 127, 118, 148, 43, 182, 213, 248, 186, 31, 119, 178, 76, 228, 187, 102, 194, 32, 13, 79, 139, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: