Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b27afa280ba1f7f7e7846ee4285d4819de7b0d2181cdfc0bfa8ac8a6cd73dc6

Tx prefix hash: 79314f2218e468b6975bf0898f0e795e78c31aa44e2090440e93830561ef88e1
Tx public key: 5720796cec40b8b57acdb92f50fa6bba14e9c10dd6b816d35b511be062d244e0
Timestamp: 1742329752 Timestamp [UTC]: 2025-03-18 20:29:12 Age [y:d:h:m:s]: 01:247:23:38:49
Block: 1242221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441273 RingCT/type: yes/0
Extra: 015720796cec40b8b57acdb92f50fa6bba14e9c10dd6b816d35b511be062d244e0021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd2d069ba7c1acec69a522a94d141d535c6e03b6a3c21513a47fe82f95b471df 0.000600000000 1729194 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": 1242231, "vin": [ { "gen": { "height": 1242221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd2d069ba7c1acec69a522a94d141d535c6e03b6a3c21513a47fe82f95b471df" } } ], "extra": [ 1, 87, 32, 121, 108, 236, 64, 184, 181, 122, 205, 185, 47, 80, 250, 107, 186, 20, 233, 193, 13, 214, 184, 22, 211, 91, 81, 27, 224, 98, 210, 68, 224, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: