Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8d380d961e6da2738ee9128f3eecd6a45bcc23e184cac093a73591a64d80b52

Tx prefix hash: b4c7d738d63869f606463b21882cf759c895d0989d1b5fd1e664de732c22dfdf
Tx public key: a953818b5b1ebf7d557928df162423e74559eff829fb01b1b5a54fe30e8c258d
Timestamp: 1743193367 Timestamp [UTC]: 2025-03-28 20:22:47 Age [y:d:h:m:s]: 01:050:16:40:05
Block: 1249354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 287318 RingCT/type: yes/0
Extra: 01a953818b5b1ebf7d557928df162423e74559eff829fb01b1b5a54fe30e8c258d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a468632aaadf1d8044a2e16936e64eda5260deb30a75172234a7c10e3f62c025 0.000600000000 1736393 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": 1249364, "vin": [ { "gen": { "height": 1249354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a468632aaadf1d8044a2e16936e64eda5260deb30a75172234a7c10e3f62c025" } } ], "extra": [ 1, 169, 83, 129, 139, 91, 30, 191, 125, 85, 121, 40, 223, 22, 36, 35, 231, 69, 89, 239, 248, 41, 251, 1, 177, 181, 165, 79, 227, 14, 140, 37, 141 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: