Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 950164bdd840fcd27d35ad91021b2df885974b08c39fe933c2ca213b9c671eef

Tx prefix hash: c825f418df6157f5e48e84a1d276baebd49d8620c13f2b0aea35c59e497d1416
Tx public key: 2ac60afce78bfc525f1f7a2efb1992a0e73b1dbacae0369c2a311df0a5cec5db
Timestamp: 1747139182 Timestamp [UTC]: 2025-05-13 12:26:22 Age [y:d:h:m:s]: 00:362:19:02:43
Block: 1282019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249510 RingCT/type: yes/0
Extra: 012ac60afce78bfc525f1f7a2efb1992a0e73b1dbacae0369c2a311df0a5cec5db02110000000e9f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1718a4b6899ce59ddf9a4ebfa6896659a0bef1fe25b8d0973329af22d25a3457 0.000600000000 1769426 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": 1282029, "vin": [ { "gen": { "height": 1282019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1718a4b6899ce59ddf9a4ebfa6896659a0bef1fe25b8d0973329af22d25a3457" } } ], "extra": [ 1, 42, 198, 10, 252, 231, 139, 252, 82, 95, 31, 122, 46, 251, 25, 146, 160, 231, 59, 29, 186, 202, 224, 54, 156, 42, 49, 29, 240, 165, 206, 197, 219, 2, 17, 0, 0, 0, 14, 159, 159, 230, 140, 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: