Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55696386f710eca19eafeb400f5b3325e95200bb8a709eb2d03434b00d7aa769

Tx prefix hash: 998e695f73bdf20e4b9e156bd6febb17e35c5bcfdf59d0fa4b67fa20c0e3544f
Tx public key: a19c98f43a82ad81891f495a09fac68791314151d710445e3543017f4398eae8
Timestamp: 1748104571 Timestamp [UTC]: 2025-05-24 16:36:11 Age [y:d:h:m:s]: 01:178:18:20:45
Block: 1290028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391807 RingCT/type: yes/0
Extra: 01a19c98f43a82ad81891f495a09fac68791314151d710445e3543017f4398eae80211000000059f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cef5560771ebae1f2e3035ed0dd0d5062d8c8c73967a80a64edfbd011ae1c2e1 0.000600000000 1777497 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": 1290038, "vin": [ { "gen": { "height": 1290028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cef5560771ebae1f2e3035ed0dd0d5062d8c8c73967a80a64edfbd011ae1c2e1" } } ], "extra": [ 1, 161, 156, 152, 244, 58, 130, 173, 129, 137, 31, 73, 90, 9, 250, 198, 135, 145, 49, 65, 81, 215, 16, 68, 94, 53, 67, 1, 127, 67, 152, 234, 232, 2, 17, 0, 0, 0, 5, 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: