Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e40afbffa4e38b0605f4e8a8fea3af6089be43b276950566e0da1ac065dad866

Tx prefix hash: 0fb673ceed4f20029e41d4514559c39fc3f4d63d0425e3da1e2f560d49988e48
Tx public key: c70fd02ee921b628abea7e87e20fb57e0091faae4733f9008d19168c343bfbfe
Timestamp: 1761871756 Timestamp [UTC]: 2025-10-31 00:49:16 Age [y:d:h:m:s]: 01:018:14:29:47
Block: 1401587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279619 RingCT/type: yes/0
Extra: 01c70fd02ee921b628abea7e87e20fb57e0091faae4733f9008d19168c343bfbfe0211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd88be0a7e103251c02db2f4c0fb3ae9673e8ef59c55955f2c8d9b62c50f2f5a 0.000600000000 1889906 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": 1401597, "vin": [ { "gen": { "height": 1401587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd88be0a7e103251c02db2f4c0fb3ae9673e8ef59c55955f2c8d9b62c50f2f5a" } } ], "extra": [ 1, 199, 15, 208, 46, 233, 33, 182, 40, 171, 234, 126, 135, 226, 15, 181, 126, 0, 145, 250, 174, 71, 51, 249, 0, 141, 25, 22, 140, 52, 59, 251, 254, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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: